SPARK PEX Prompt Library — Interactive Dashboard

📓

The Notebook First Rule — Non-Negotiable

Write every prompt in full PEX format in your physical notebook before typing it into any AI tool. Physical writing activates System 2 (slow, deliberate) thinking. Typing directly activates System 1 (fast, reflexive) thinking — the source of vague prompts and prompt-and-paste behaviour.

🔍

No prompts match your current filters.
Try adjusting the role, topic, or search term.

Sprint 1 — Context Research & Project Scoping

Market Context Analysis S1

Scout▼

Purpose

Example

Similar to how a market entry brief would be structured for a consulting firm entering an emerging market — factual, concise, with clear takeaways at the end of each section.

Expected Output

A structured report with 4 sections: (1) Market Overview, (2) Key Competitors (max 5, one differentiator each), (3) Top 3 Customer Pain Points with evidence, (4) Key Risks to Validate. Max 500 words total.

I am building a [product/service] for [target audience] in [city/region]. I need to understand the competitive landscape, the top 3 user pain points, and any regulatory or cultural factors that could affect our approach. Produce a structured report with 4 sections: 1. Market Overview (2–3 sentences) 2. Key Competitors (max 5, one differentiator each) 3. Top 3 Customer Pain Points with brief evidence 4. Key Risks to Validate before Sprint 2 Write in the style of a consulting market entry brief. Clear, factual, no padding. Max 500 words total.

Sprint Milestone Definition S1

Manager▼

Purpose

I am running a SPARK Lab team project on [project topic]. I need to define 4 concrete sprint milestones across a 4-week programme that are achievable, team-visible, and progressively build toward a Demo Day presentation.

Example

A milestone should be a thing (a document, a prototype, a tested feature), not a process. For example: "Sprint 1 milestone: A 1-page validated user persona document with 3 real insights from primary research."

Expected Output

A numbered list of 4 sprint milestones in SMART-P format. Each milestone: one sentence description of the deliverable + one sentence defining done criteria.

I am running a SPARK Lab team project on [project topic] with 3–4 team members (Manager, Builder, Scout). I need 4 sprint milestones — one per week — that lead to a Demo Day presentation. Requirements: - Each milestone must be a concrete deliverable (a document, a prototype, a page, a tested feature) - Must be achievable in one week's work by the whole team - Must build progressively toward the final Demo Day output Produce a numbered list of 4 milestones in SMART-P format. Each: one sentence describing the deliverable + one sentence defining what "done" looks like.

User Persona Generation S1

Scout▼

Purpose

I need to create a realistic user persona for [product] targeting [audience description]. This persona will guide our Builder's design and content decisions throughout the programme.

Example

Similar to a UX persona card from design thinking methodology — human, specific, with a name, a quote, and real frustrations that our product can address.

Expected Output

One persona card with: name, age, occupation, daily routine (2 sentences), top 3 frustrations relevant to our product, one direct quote, and one thing they wish existed. Plain text, no bullet points.

Create a realistic user persona for [product/service] targeting [audience description, e.g. "college graduates in their first year of employment in Chennai"]. Make the persona feel like a real human being, not a demographic category. Include: - Name, age, occupation - Daily routine (2 sentences) - Top 3 frustrations relevant to our product - One direct quote from their perspective - One thing they genuinely wish existed Format: flowing narrative, no bullet points. Tone: grounded and specific, not generic.

Secondary Research Deep Dive S1

Scout▼

Purpose

I need to collect credible secondary research on [topic] that will inform our Sprint 1 findings. I want recent data, relevant case studies, and expert opinions — not generic summaries.

Example

Like the research section of a McKinsey Industry Insight: data-backed, with source type attribution (e.g. "industry report, 2024"), prioritising actionable insight over description.

Expected Output

5 key findings, each with: (a) the insight in one sentence, (b) the type of source, (c) why it is relevant to [project]. End with one sentence summarising the most important implication for our team.

I need secondary research on [topic] to inform the first sprint of our project on [project description]. For each of the 5 most important findings: a) State the insight in one clear sentence b) Indicate the type of source (industry report / academic study / news / expert opinion) c) Explain in one sentence why this matters for our specific project Close with: "The single most important implication for this team is: [sentence]." Flag any area where current data is hard to find — that is a gap we need to research ourselves.

Team Charter Draft S1 · Kickoff

Manager▼

Purpose

Our team is starting a 4-sprint SPARK Lab programme. I need to draft a one-page team charter that defines roles, working norms, decision rules, and conflict resolution approach before we begin Sprint 1 work.

Example

Like a lightweight team agreement document used in Agile kick-offs — practical, not legalistic. Should be something the team can refer back to when disagreements arise.

Expected Output

A one-page charter with 5 sections: Roles (3 sentences), Working Norms (5 bullet points), Communication Rules (3 bullet points), Decision Rule (1 sentence), Conflict Resolution (3 steps). Leave [blank] placeholders for team-specific choices.

Draft a one-page team charter for a 3-person SPARK Lab team (Manager, Builder, Scout) working on [project topic] over 4 weeks. Include 5 sections: 1. Roles (one sentence per role: Manager, Builder, Scout) 2. Working Norms (5 norms the team agrees to uphold) 3. Communication Rules (how/when the team communicates — WhatsApp norms, meeting frequency) 4. Decision Rule (how the team makes decisions when they disagree) 5. Conflict Resolution Steps (3-step process for resolving tensions) Use [BLANK] for team-specific choices (e.g. meeting day). Keep it under one A4 page. Practical, not corporate.

User Interview Question Set S1

Scout▼

Purpose

I need to conduct 3–5 short user interviews (15 min each) to validate our problem hypothesis. I need a structured question set that surfaces real pain points without leading the interviewee toward our assumptions.

Example

Like the interview scripts used in Google Design Sprints or IDEO human-centred design research — open-ended, empathic, free of solution bias.

Expected Output

10 interview questions in 3 blocks: Warm-up (3), Core Problem Exploration (5), Closing (2). For each question: note whether it is open-ended (OE) or probing (PR). Flag any leading-bias question.

I need a 15-minute user interview script to validate this problem hypothesis: [describe your hypothesis]. Target interviewee: [describe who you are interviewing]. Produce 10 questions in 3 blocks: BLOCK 1 — Warm-up (3 questions): Build rapport, understand context BLOCK 2 — Core Problem Exploration (5 questions): Surface real experiences, not opinions BLOCK 3 — Closing (2 questions): Future state and willingness to act Label each question: (OE) open-ended or (PR) probing follow-up. Flag any question that risks leading the interviewee toward our hypothesis with ⚠.

Sprint 2 — Core Building & Content Generation

First Draft Content Generator S2

Builder▼

Purpose

I need to write [type of content: landing page / pitch section / product description] for [project]. The content needs to connect emotionally with [target user] while clearly communicating [core value proposition].

Example

Tone: warm, direct, zero jargon. Similar to how Notion or Basecamp write their homepage copy — human, specific, no buzzwords. Sentences under 20 words.

Expected Output

One headline (max 10 words), one subheadline (max 20 words), three benefit statements (one sentence each), and one call-to-action phrase. Total: under 100 words.

Write [landing page / pitch section / product description] copy for [project name], a [one-sentence description]. Target user: [user persona description] Core value proposition: [one sentence] Tone requirements: - Warm, direct, zero jargon - Sentences under 20 words - No buzzwords (no "revolutionary", "seamless", "cutting-edge") Deliver: 1. Headline (max 10 words) 2. Subheadline (max 20 words) 3. Three benefit statements (one sentence each) 4. One call-to-action phrase Total under 100 words.

Business Model Canvas — Quick Build S2

Builder▼

Purpose

I need to build a first-draft Business Model Canvas for [project/startup idea] to guide our Sprint 2 and 3 work and to have a structured framework for our Demo Day presentation.

Example

Based on the Osterwalder Business Model Canvas format — 9 blocks, each answered specifically for our context, not generically.

Expected Output

All 9 BMC blocks filled out for [project], 2–4 bullet points per block, in a table or clearly labelled sections. Be specific — no placeholders or vague statements.

Build a Business Model Canvas for [project name]: [one-sentence description of what it does and for whom]. Fill all 9 blocks of the Osterwalder BMC: 1. Customer Segments 2. Value Propositions 3. Channels 4. Customer Relationships 5. Revenue Streams 6. Key Resources 7. Key Activities 8. Key Partnerships 9. Cost Structure Requirements: - 2–4 bullet points per block - Be specific to this project — no generic placeholders - Flag any block where you are making assumptions (mark with ⚠)

Prompt Comparison — A/B Scout Test S2

Scout▼

Purpose

I need to find the most effective prompt for [specific task] by testing two alternative approaches and comparing the quality of their outputs. This comparison will be added to our team Prompt Library.

Example

Approach A will be broad and exploratory. Approach B will be highly specific and constrained. I will assess each on three criteria: accuracy, relevance to our project, and usability without editing.

Expected Output

For each approach: the full prompt used, the AI's output (summarised in 3 bullet points), and a 2-sentence quality assessment. Final recommendation: which prompt to use in Sprint 3 and why.

I am testing two prompting approaches for the task: [describe task]. APPROACH A (broad): [Write your exploratory prompt here] APPROACH B (specific): [Write your constrained prompt here] For each approach, produce: 1. A summary of the AI's output in 3 bullet points 2. A 2-sentence quality assessment: accuracy + usability without editing 3. One thing this approach does better than the other Final line: "Recommended prompt for Sprint 3: A or B, because [one sentence]."

Product Wireframe Specification S2

Builder▼

Purpose

I need to create a text-based wireframe specification for [product/feature] so our team can build and review the core user flow before we invest time in visual design.

Example

Like a user story map or low-fidelity screen description — describe each screen in plain language, what elements it contains, and what happens when the user acts. No design jargon needed.

Expected Output

For each of the 3–5 core screens: screen name, primary user goal, list of elements (header, buttons, inputs, text), and one sentence describing the main action that moves to the next screen.

Write a text-based wireframe specification for [product name]. Core user journey: [describe in 2 sentences — e.g. "User opens app, completes a 3-step onboarding, then reaches the main dashboard."] Target user: [persona name and description] For each of the 3–5 core screens, provide: - Screen name - Primary user goal on this screen (one sentence) - Elements present (list: header, buttons, text fields, images etc.) - The single most important action and where it leads Keep it in plain English — no design or technical jargon. A non-technical team member should be able to sketch this from your description.

Sprint Task Breakdown & Assignment S2

Manager▼

Purpose

I am the team Manager and need to break the sprint goal into specific tasks, assign them by role, and set daily checkpoints — so every team member knows exactly what to do and when.

Example

Like a Kanban sprint board in text form — each task has an owner (role), an estimated time, and a clear "done" definition. No ambiguity about who does what.

Expected Output

A task table with columns: Task Name | Owner Role | Estimated Hours | Done Criteria. Minimum 9 tasks (3 per role). Followed by a 5-day check-in schedule (what to review on each day).

I am the Manager of a SPARK Lab team. Sprint goal: [describe goal]. Team roles: Manager (coordination, documentation), Builder (product/content creation), Scout (research, testing, feedback). Create a sprint task breakdown: - Minimum 9 tasks, 3 per role - For each task: Task Name | Owner Role | Estimated Hours | Done Criteria (one sentence) Then produce a 5-day check-in schedule: Day 1: [what Manager reviews] Day 2–4: [midweek checkpoint focus] Day 5: [end-of-sprint review criteria] No vague tasks. Every task must have a measurable done condition.

Pitch Deck Slide Outline S2

Builder▼

Purpose

I need to draft the outline for a 10-slide pitch deck for [project]. The deck should work for our Demo Day presentation and could later be adapted for an investor or accelerator application.

Example

Following the Y Combinator or Sequoia pitch structure: problem → solution → market → traction → team → ask. Each slide has one job and one key message. No text walls.

Expected Output

A 10-slide outline: slide number, slide title, one-sentence key message, and 3 bullet points of content to include. Note which slide is most important visually and why.

Create a 10-slide pitch deck outline for [project name]: [one-sentence description]. Context: - Problem we solve: [describe] - Our solution: [describe] - Target market: [describe] - Team: Manager, Builder, Scout Structure each slide as: Slide [N] — [Title] Key Message: [one sentence - what the audience must remember from this slide] Content: [3 bullet points of what goes on this slide] After the outline, add one line: "The slide that will make or break your pitch is Slide [N] because [reason]."

Sprint 3 — Refinement, Iteration & Quality

Output Quality Review & Improvement S3 · Review

All Roles▼

Purpose

I have a draft [document/section/feature] that was produced in Sprint 2. I need to identify its three biggest weaknesses and get specific improvement suggestions before our Sprint 3 final build.

Example

Act as a senior editor or product reviewer — honest, direct, constructive. Not someone who praises for encouragement, but someone who gives the feedback that makes the work better.

Expected Output

Three numbered weaknesses, each with: (a) what the problem is, (b) why it matters, (c) one specific suggestion for fixing it. No praise unless it identifies what to keep.

I am going to paste a draft [document/section/feature description] below. Review it as a senior [editor / product manager / strategist] would. [PASTE YOUR DRAFT HERE] Identify the 3 biggest weaknesses. For each: a) What is the problem? b) Why does it matter for the project's goal? c) One specific, actionable fix Do not pad with praise. If something is working well and should be kept, note it briefly. Focus on what needs to change.

Devil's Advocate — Challenge Assumptions S3

Scout▼

Purpose

My team has been working on [project] for 3 weeks. We need someone to challenge our core assumptions before Demo Day so we can address the hardest questions in our presentation.

Example

Act as a skeptical investor or a critical mentor who genuinely wants us to succeed but is not willing to let weak assumptions go unchallenged. The harder the question, the better.

Expected Output

5 challenging questions a skeptic would ask, plus one sentence explaining the risk each question points to. Then: one suggestion for how to address the most critical one.

My team has built [brief project description] over 3 weeks. Here is a summary of what we have done: [PASTE YOUR PROJECT SUMMARY — 3–5 sentences] Act as a skeptical investor who wants us to succeed but will not let weak assumptions slide. Produce: 1. Five hard questions a skeptic would ask (one sentence each) 2. For each question: one sentence on the risk it points to 3. At the end: "The most critical question to address in your Demo Day presentation is #[N] because [one sentence]."

Social Media Content Pack S3

Builder▼

Purpose

I need to create a launch content pack for [project/brand] for Instagram and LinkedIn, communicating our value proposition in a way that feels human and shareable, not corporate.

Example

Tone similar to how Oatly or Innocent Drinks write their social content — self-aware, specific, personality-driven. The audience should feel like they are talking to a person.

Expected Output

3 Instagram captions (max 150 words each), 2 LinkedIn posts (max 200 words each), and 5 hashtag suggestions per platform. Each post should have a different angle on the same core message.

Create a social media content pack for [project/brand name]: [one-sentence description]. Core message to communicate: [value proposition] Target audience: [description] Brand personality: [e.g. "warm and practical" / "bold and irreverent" / "calm and expert"] Produce: - 3 Instagram captions (max 150 words each, different angles on the same message) - 2 LinkedIn posts (max 200 words each, professional but not corporate) - 5 hashtags per platform Each post must start with a hook that stops the scroll. No hashtag stuffing. No "We are excited to announce" openings.

User Feedback Synthesis S3 · Review

Scout▼

Purpose

I have collected feedback from [N] people who tested our Sprint 2 prototype. I need to synthesise this feedback into clear, actionable themes so the Builder knows exactly what to fix in Sprint 3.

Example

Like a UX research debrief report — themes identified from multiple data points, not a list of individual opinions. Pattern first, then specific examples as evidence.

Expected Output

3–5 feedback themes in priority order. For each: theme name (2–4 words), one sentence describing the pattern, one example quote, and one actionable fix the Builder can implement this sprint.

I collected feedback from [N] users who tested [prototype/product description]. Here are the raw notes: [PASTE YOUR NOTES HERE] Synthesise this into actionable themes using this format: THEME [N] — [2–4 word label] Pattern: [one sentence describing the common experience] Evidence: [one direct quote or observation that best represents this theme] Fix for Builder: [one specific, implementable action this sprint] Order themes by impact: highest-impact fix first. End with: "If we only fix one thing before Demo Day, it should be Theme [N] because [reason]."

Sprint Retrospective Facilitation S3 · Retro

Manager▼

Purpose

I need to run a 20-minute retrospective for my team at the end of Sprint 3 that helps us identify what slowed us down, what we should keep, and what one change to make in our final sprint.

Example

Based on the Start / Stop / Continue retro format — structured but conversational. The Manager facilitates, each person speaks, and the team agrees on one concrete action before ending.

Expected Output

A 20-minute facilitation script with: opening (2 min), 3 round-robin questions (12 min), synthesis prompt (4 min), closing commitment (2 min). Include the exact question wording for each section.

Write a 20-minute Sprint Retrospective facilitation script for a team of 3 (Manager, Builder, Scout) at the end of Sprint 3. Use the Start / Stop / Continue framework. Structure: [0–2 min] Opening: reset tone, remind the team this is a safe space [2–14 min] Three rounds (Manager reads question, everyone answers in turn): Round 1 — STOP: What slowed us down or created friction? Round 2 — START: What should we do in Sprint 4 that we haven't done yet? Round 3 — CONTINUE: What worked well and must not be dropped? [14–18 min] Synthesis: Manager summarises and proposes one team commitment [18–20 min] Close: each person says one word describing how they feel going into Sprint 4 Provide the exact wording for each prompt. Keep tone warm, not corporate.

Email Outreach Template Pack S3

Builder▼

Purpose

I need 3 email templates for [project] to use during Sprint 3: one for cold outreach to potential users, one for follow-up after a demo, and one for sharing our Demo Day invite.

Example

Like the email style used by early-stage startups — brief (under 100 words), specific to the recipient, with one clear ask. Not a newsletter. Not a pitch deck via email.

Expected Output

3 email templates each with: Subject line, body (under 100 words), one call to action. Leave [brackets] for personalisation. Note the optimal send time for each.

Write 3 email templates for [project name]: [one-sentence description]. Template 1 — Cold Outreach (to someone who has not heard of us yet) Template 2 — Follow-up After Demo (to someone who saw a short presentation) Template 3 — Demo Day Invitation (to invite them to our final event) For each template: - Subject line (max 8 words, no click-bait) - Body (max 100 words — specific, human, no corporate language) - One clear call to action - [BRACKETS] for any personalisation fields - Note: "Best time to send: [day/time]"

Sprint 4 — Demo Day Preparation

Demo Day Narrative Builder S4 · Demo Day

Manager▼

Purpose

I need to build a compelling 10-minute Demo Day presentation narrative for [project]. The story must be coherent enough for a general audience to understand what we built, why, and what we learned.

Example

Structured like a TED talk opening — start with the human problem, not the solution. Make the audience care about the problem before they hear about what we built.

Expected Output

A 5-section presentation outline: (1) Opening hook, (2) The problem, (3) Our approach, (4) What we built, (5) What we learned. Each section: 2–3 bullet points + estimated speaking time.

Help me structure a 10-minute Demo Day presentation for our project: [project name and one-sentence description]. Key facts: - Problem we addressed: [describe] - Our approach: [describe] - What we actually built: [deliverables] - Most surprising thing we learned: [describe] - What we would do next with more time: [describe] Build a 5-section narrative outline: 1. Opening hook (2 min) — make the audience care about the problem 2. The problem (2 min) — specific, human, relatable 3. Our approach (2 min) — how we thought about solving it 4. What we built (2 min) — show, don't tell 5. What we learned (2 min) — honest, including what surprised us Each section: 2–3 bullet points + estimated timing.

Q&A Preparation — Anticipate Hard Questions S4 · Demo Day

All Roles▼

Purpose

I want to prepare our team for the Demo Day Q&A by anticipating the 5 most likely questions from the audience and preparing clear, confident, honest answers — including for questions we don't have perfect answers to.

Example

Treat "I don't fully know yet" as a valid, even positive answer when combined with "and here's how we would find out" — intellectual honesty is more impressive than false confidence.

Expected Output

5 likely audience questions, each with: a 2–3 sentence confident answer, and a note on who on the team should answer it based on their role.

Our Demo Day project is: [project name and description]. Our team has: a Manager (who coordinated), a Builder (who built [X]), and a Scout (who researched [Y]). Generate the 5 most likely audience questions after a 10-minute presentation on this project. For each question: 1. The question (as an audience member would ask it) 2. A 2–3 sentence honest, confident answer (including "we don't know yet and here's how we'd find out" where appropriate) 3. Role note: "Best answered by: Manager / Builder / Scout because [one reason]"

Presentation Speaker Notes S4 · Demo Day

Builder▼

Purpose

I need to convert our pitch deck outline into per-slide speaker notes — short enough to memorise, specific enough to sound natural, not scripted. Each speaker should know exactly what to say on their slide.

Example

Like the notes a confident presenter uses — talking points, not a script. 3–4 key phrases per slide, not full sentences to read aloud. Conversational and direct.

Expected Output

For each of our [N] slides: slide title, the speaker (role), 3 talking points as bullet phrases (not full sentences), and one transition sentence to the next slide.

Convert the following pitch deck outline into speaker notes. Our Demo Day presentation has [N] slides. [PASTE YOUR SLIDE OUTLINE HERE] For each slide, produce: - Slide [N]: [Title] - Speaker: [Manager / Builder / Scout] - Talking Points: 3 bullet phrases (keywords only — not full sentences to read) - Transition: One natural sentence to bridge to the next slide Tone: conversational and confident — not stiff. The presenter should sound like they're telling a story, not reading a report.

Demo Day Countdown Checklist S4 · Demo Day

Manager▼

Purpose

We are [N] days away from Demo Day. I need a day-by-day countdown checklist that keeps the whole team aligned on what needs to happen, who owns it, and when it must be done.

Example

Like an event day run-sheet crossed with a launch countdown — each day has 2–3 must-complete actions. The Manager can use this as a daily stand-up agenda for the final week.

Expected Output

A day-by-day checklist for the final [N] days, with: date label, 2–3 tasks, task owner (role), and a "Gate" — the one thing that must be done before moving to the next day.

Demo Day is in [N] days. Create a countdown checklist for my 3-person team (Manager, Builder, Scout). For each day, produce: - Day label (e.g. "Day 5 — Rehearsal Day") - 2–3 specific tasks (with owner role) - One Gate: the single thing that cannot be skipped before Day N–1 The final day (Demo Day) should include: pre-event setup checklist (30 min before), presentation order, and a post-event debrief prompt. Keep it tight. No padding. This is a working document, not a project report.

Kickoff Event — Team Launch Prompts

Kickoff Session Agenda Kickoff

Manager▼

Purpose

I need to design the agenda for our team's first session — the kickoff. It should set the right tone, align everyone on the project goal, and produce 2 concrete outputs (team charter draft and Sprint 1 plan) by the end.

Example

Like the first session of a startup accelerator — energising, structured, and ending with everyone knowing exactly what they are doing next week. Not a lecture. An activation.

Expected Output

A 2-hour kickoff agenda with time blocks, activity descriptions (2 sentences each), materials needed, and facilitator notes. Outputs section at the end listing what the team leaves with.

Design a 2-hour team kickoff session agenda for a 3-person SPARK Lab team starting a project on [topic]. Structure: - 0–15 min: Icebreaker + team intro (suggest a specific activity) - 15–35 min: Project overview — why this matters, what success looks like - 35–60 min: Role alignment — what Manager, Builder, Scout each own - 60–85 min: Team charter co-creation (use the Stop / Start / Continue format adapted for agreements) - 85–110 min: Sprint 1 planning — break down first week tasks - 110–120 min: Close and commitment (each person states one public commitment) For each block: activity description (2 sentences), facilitator prompts, materials needed. End with: "Team leaves with: [list of 3 concrete outputs]."

Problem Statement Sharpener Kickoff · S1

Scout▼

Purpose

Our team has a rough idea for [project]. I need to sharpen it into a clear problem statement that is specific enough to guide our research in Sprint 1 and test with real users.

Example

Like the "How Might We" reframe used in design thinking — the problem should be neither too narrow (limits solutions) nor too broad (makes research unfocused).

Expected Output

Three alternative problem statement formulations (one too narrow, one too broad, one just right), then a recommended "How Might We" statement for Sprint 1 research, with a one-sentence rationale.

Our rough project idea is: [describe your idea in 2–3 sentences]. Help us sharpen it into a testable problem statement. Produce: 1. Version A — Too Narrow: [problem statement that limits our options too much] 2. Version B — Too Broad: [problem statement so wide it is impossible to research] 3. Version C — Calibrated: [the right level of specificity] 4. "How Might We" framing: a single HMW question based on Version C 5. One sentence: "This HMW is well-calibrated because [reason]." Do not pick our idea apart — help us find the sharpest version of what we are trying to solve.

Project Naming & Brand Brief Kickoff · S1

Builder▼

Purpose

Our team needs a project name and a short brand brief before we begin building. The name should be memorable, available (as a Google search term), and reflect our value proposition without explaining it literally.

Example

Like the naming approach used for companies like Notion, Slack, or Figma — short, one or two syllables, easy to spell, with a name that grows into its meaning through use, not a name that describes itself.

Expected Output

5 name options (each with a one-sentence rationale), a recommended choice with a 3-sentence rationale, and a one-paragraph brand brief covering: personality, tone of voice, and one thing the brand should never be.

Generate a project name and brand brief for our startup idea: [describe project in 2–3 sentences]. Target audience: [describe] Values we want to project: [e.g. "clarity, warmth, ambition"] Things we want to avoid: [e.g. "tech jargon, corporate tone, anything that sounds like a bank"] Produce: 1. 5 name options (one sentence rationale each) 2. Recommended name with 3-sentence rationale 3. One-paragraph brand brief covering: - Brand personality (3 adjectives with explanation) - Tone of voice (how we write, 2 sentences) - One thing this brand should never be or say The names should be short, spell-checkable, and not already a major brand.

Sprint Review Events — End-of-Sprint Presentations

Sprint Review Presentation Brief Sprint Review

Manager▼

Purpose

At the end of Sprint [N], our team needs to present our progress to the trainer and other teams in a 5-minute review. I need to structure what we say so it is concise, honest, and invites useful feedback.

Example

Like a stand-up on steroids — covers what we did, what we learned, what slowed us down, and what we need from the room. Not a polished pitch. An honest work-in-progress update.

Expected Output

A 5-minute script outline with 4 sections (1 min each + 1 min Q&A setup), with talking points per section and a specific feedback request question at the end.

Write a 5-minute Sprint [N] Review presentation outline for our team working on [project]. This sprint's goal was: [describe] What we actually completed: [list 2–3 items] What we did not complete and why: [honest explanation] What surprised us this sprint: [one insight] Structure: [0–1 min] What we set out to do (goal + milestone) [1–2 min] What we actually built/found/tested (be specific) [2–3 min] What we learned — including what did not work [3–4 min] What we are doing in Sprint [N+1] and why [4–5 min] Our specific feedback request: "We need the room's input on [one precise question]." Tone: honest and direct. We want useful feedback, not applause.

Sprint Artefact Documentation Sprint Review

Scout▼

Purpose

I need to document our Sprint [N] work into a structured artefact summary that can be shared with the trainer, added to our Drive folder, and serve as evidence of our learning process.

Example

Like the "Sprint Retrospective Document" used by agile teams — factual, with descriptions of real outputs, plus a clear account of what decisions were made and why.

Expected Output

A one-page sprint summary with: sprint goal, 3 key outputs (with descriptions), 2 decisions made and their rationale, 1 assumption we tested, and 1 open question going into the next sprint.

Help me write a structured Sprint [N] artefact summary for our team project on [topic]. SPRINT [N] SUMMARY — [Project Name] Sprint Goal: [one sentence] Key Outputs: 1. [Name of output]: [2-sentence description of what it is and how it was made] 2. [Name of output]: [same format] 3. [Name of output]: [same format] Key Decisions Made: 1. We decided to [decision] because [rationale — one sentence] 2. We decided to [decision] because [rationale — one sentence] Assumption Tested: We assumed [X]. We found [Y]. Open Question for Sprint [N+1]: [the one most important thing we still don't know] Keep it factual. A third party reading this should understand what the team did without any verbal explanation.

Peer Feedback Exchange Sprint Review · Retro

All Roles▼

Purpose

I want to give honest, constructive feedback to my teammate [role] after Sprint [N]. I need a structure that is direct but not hurtful, specific but not petty, and focused on what changes behaviour, not just what describes it.

Example

Like the SBI (Situation-Behaviour-Impact) feedback model used in professional coaching — grounded in specific observations, not personality judgements.

Expected Output

A feedback message structured in 3 parts: (1) Observation (what I saw, no interpretation), (2) Impact (the effect on the team or project), (3) Request (a specific, actionable change for the next sprint). Max 150 words.

Help me write constructive peer feedback for my teammate [role: Manager / Builder / Scout] after Sprint [N]. Situation I want to address: [describe one specific situation — what happened, when] What I observed: [describe the behaviour, not the person — what they did or did not do] The impact on me or the team: [describe concretely] What I want them to do differently: [one specific, actionable change] Format using the SBI model: Situation: [brief context] Behaviour: [what I observed — factual, non-judgmental] Impact: [the effect — use "I" statements] Request: "In Sprint [N+1], I would find it helpful if you [specific action]." Keep under 150 words. Do not start with "I feel like you never…"

Retrospective Events — Between-Sprint Reflection

Mid-Programme Team Retrospective Retro

Manager▼

Purpose

We are at the mid-point of our SPARK Lab programme. I need to run a structured retrospective that surfaces real friction, resets team energy, and produces one concrete process improvement we commit to implementing immediately.

Example

Like the sprint retros used in software teams — psychologically safe, structured so everyone speaks, and ending with one committed action not a list of aspirations.

Expected Output

A 25-minute retro plan with 4 phases: check-in, data collection, insights, and decision. Include exact facilitator prompts for each phase.

Design a 25-minute retrospective for a 3-person team at the midpoint of a 4-sprint programme on [project topic]. Four phases: Phase 1 — Check-in (3 min): Each person answers: "One word for how Sprint [N] felt." Phase 2 — Data (10 min): Each person answers: "What slowed your work? What helped most?" Phase 3 — Insights (7 min): Manager facilitates: "What pattern do we see across all three answers?" Phase 4 — Decision (5 min): Team agrees on ONE process change for next sprint written as: "Starting [day], we will [action] instead of [current behaviour]." Provide facilitator notes for each phase — what to do if the room goes quiet, how to handle disagreement.

Personal Learning Reflection Retro · Any Sprint

All Roles▼

Purpose

I want to reflect on what I have learned so far in the programme — not just what we built, but what I have learned about working with AI, about my role, and about myself as a professional.

Example

Like a journal entry structured for professional growth — honest, specific, and focused on what I will do differently, not just what happened.

Expected Output

5 reflection prompts I should write answers to in my notebook (not AI-generated answers — just the right questions to guide my thinking). Then one synthesis question at the end.

I am [role: Manager / Builder / Scout] in a SPARK Lab team, [N] weeks into the programme. Give me 5 deep reflection prompts I should answer in my physical notebook — not AI-generated answers, just the right questions to make me think clearly about: 1. What I assumed about AI tools before this programme vs. what I have actually discovered 2. A moment where I felt genuinely capable or proud of my contribution 3. The biggest mistake I made and what it cost us as a team 4. How my relationship with the other two team members has evolved 5. The skill I want to develop most before the programme ends End with one synthesis question: "If I had to name the single most important thing I have learned so far, it would be _____."

Advanced — Cross-Sprint & Role-Specific Techniques

Team Prompt Library Entry Any Sprint

Scout▼

Purpose

After every significant AI interaction, I need to document the prompt in our shared Google Sheets Prompt Library, including its quality rating and what I would change next time.

Example

Like a lab notebook entry — factual, short, reproducible by a teammate who was not in the room. If they read my entry, they should be able to replicate the result.

Expected Output

Help me write a Prompt Library entry for a prompt I just used. The prompt I used was for: [describe the task] The AI tool I used: [Claude / ChatGPT / Gemini / other] The output I received was: [brief description — 2 sentences] My quality rating (1–5): [N] Produce a complete library row: Prompt ID: [SNYY — Sprint N, sequential number] Sprint: [N] Role: [Manager / Builder / Scout] Task Category: [Research / Content / Review / Planning / Communication] Purpose: [20-word summary] Output Quality: [1–5] What I'd Change: [one specific prompt improvement] Rationale for score: [2 sentences — what worked and what did not]

Manager: Handling Team Tension Any Sprint

Manager▼

Purpose

There is tension in our team around [specific situation]. As Manager, I need to address it directly in our next check-in without damaging trust or derailing our sprint progress.

Example

Like the conversation frameworks used in non-violent communication (NVC) — name the observation without blame, describe the impact, and invite a collaborative solution. No drama, no avoidance.

Expected Output

A 3-step conversation guide: (1) Opening statement (what to say in the first 30 seconds), (2) The question to open dialogue, (3) A proposed resolution to offer if the conversation stalls. Under 150 words total.

I am the Manager of a SPARK Lab team. There is tension around: [describe the situation — e.g. "one Builder is not completing tasks by the agreed deadline" or "the Scout and Builder disagree on research findings"]. Help me structure a direct, non-confrontational conversation for our next check-in. Produce: 1. Opening Statement (30 seconds): What to say to name the situation without blame 2. Dialogue Question: The one question that invites honest, collaborative response 3. Resolution Offer: A proposed way forward if the other person is stuck or defensive Use NVC-style language: "I notice [observation]. The impact on the team is [specific effect]. I want us to find [collaborative outcome]." Keep under 150 words. No corporate HR language.

Visual Asset Prompt (Image AI) S2–S4

Builder▼

Purpose

I need to generate a visual asset (hero image / illustration / logo concept) for [project] using an AI image tool. I need a prompt that gives consistent, on-brand results without generic stock-photo aesthetics.

Example

Reference visual: [describe a real image or style — e.g. "editorial illustration from the New Yorker" / "product photo on white background, soft shadows, iPhone 16 style" / "flat vector icon, warm earth tones"]. Be specific.

Expected Output

A ready-to-paste image generation prompt (for Midjourney / DALL-E / Ideogram) with: subject, environment/background, style reference, mood, lighting, and aspect ratio. Under 80 words.

Write an AI image generation prompt for [describe what you want: hero image / logo concept / product mockup / illustration]. Project: [project name and description] Brand personality: [e.g. "warm, approachable, modern" / "bold, technical, minimal"] Style reference: [name a specific visual style or comparable brand] Your prompt must specify: - Subject (what/who is in the image) - Background / environment - Visual style (illustration, photography, 3D, flat design, etc.) - Mood and lighting - Aspect ratio (16:9 / 1:1 / 9:16) Keep under 80 words. Avoid vague words like "beautiful" or "amazing." Be technically specific.

Chain-of-Thought Reasoning Prompt Any Sprint

All Roles▼

Purpose

I am facing a complex decision or problem and need the AI to reason through it step by step — not just give me an answer, but show its thinking so I can spot where it goes wrong or where I disagree.

Example

Like asking a consultant to "think out loud" — the value is the reasoning process, not just the final recommendation. I want to see each assumption, each trade-off, each step in the logic chain.

Expected Output

Numbered reasoning steps (minimum 5), each with: the step, the assumption behind it, and any alternative interpretation. Final answer in one sentence at the end, clearly labelled.

I need you to reason through this problem step by step before giving me any answer. Problem: [describe your decision or question in 2–4 sentences] Context: [relevant background — what you know, what you have tried, what the constraints are] Think step by step. For each step: 1. State what you are figuring out 2. Name the assumption behind your reasoning 3. Mention any important alternative interpretation you are setting aside After at least 5 reasoning steps, end with: CONCLUSION: [one sentence answer] CONFIDENCE: High / Medium / Low — because [one sentence] Do not jump to the conclusion. The quality of your reasoning matters more than the speed of your answer.

Competitor Deep Dive S1–S2

Scout▼

Purpose

I need to analyse 3 competitors to [project] so that the Builder can make informed design and positioning decisions, and so the Manager can articulate our differentiation clearly on Demo Day.

Example

Like a competitive intelligence brief from a product team — factual, focused on what each competitor does well that we should learn from, and what gap they leave that we can fill.

Expected Output

For each of 3 competitors: name, one-line description, 2 strengths, 1 weakness, and 1 gap they leave open. End with: our best differentiation angle in one sentence based on this analysis.

Analyse 3 competitors to [our project: brief description]. Our target user: [describe] Our core value proposition: [one sentence] For each competitor, produce: Competitor [N]: [Name] - What they do (1 sentence) - Their 2 biggest strengths (relative to our target user) - Their most significant weakness - The gap they leave open that we could fill Close with: "Based on this competitive landscape, our strongest differentiation angle is: [one sentence describing what makes us different in a way that matters to our target user]." Be specific — name real companies or projects if you know them. Flag as ⚠ where you are estimating.

Explainer Video Script (90 sec) S3–S4

Builder▼

Purpose

I need to write a 90-second explainer video script for [project] that we can record during Sprint 3 or 4 and use on our landing page and Demo Day. It should make someone understand our product in 90 seconds, even if they have never heard of us.

Example

Tone and pacing similar to the Dropbox explainer video (2007) — conversational, relatable, zero jargon, with a clear before/after story structure. Short sentences. Real human problem first.

Expected Output

A 90-second script (≈225 words) with time-coded sections (0–15s, 15–45s, 45–75s, 75–90s), screen direction notes in [brackets], and a word count at the end.

Write a 90-second explainer video script for [project name]: [one-sentence description]. Target viewer: [describe — who watches this and what do they already know?] The problem we solve: [describe in plain language] Our solution: [describe in plain language — no technical jargon] The desired feeling after watching: [e.g. "I understand this and I want to try it"] Script structure: [0–15s] Hook: make the viewer feel the problem in their own life [15–45s] Introduce the problem — specific, relatable, not abstract [45–75s] Introduce our solution — show it working, not just describe it [75–90s] Call to action — what should the viewer do next? Include [screen direction] notes in brackets. Total: ≈225 words. End with: "Word count: [N] words | Estimated read time at normal pace: [N] seconds."

Weekly Progress Report (Upward) Any Sprint

Manager▼

Purpose

I need to write a weekly update for our trainer or programme coordinator — a brief, professional summary of what we accomplished, what is at risk, and what we need help with. It should take them under 2 minutes to read.

Example

Like the weekly update emails used by startup founders communicating with their investors — structured, honest, short. RAG (Red / Amber / Green) status for each deliverable is ideal.

Expected Output

A 5-section email: (1) One-line week summary, (2) 3 key accomplishments, (3) Status of sprint milestone (RAG), (4) One risk or blocker, (5) One specific request for support. Under 200 words.

Write a weekly progress report email for Sprint [N], Week [N], from [project name] team. This week's accomplishments: 1. [Describe what was completed] 2. [Describe what was completed] 3. [Describe what was completed] Sprint milestone status: [On track / At risk / Behind — and why in one sentence] Current blocker: [describe one blocker that is slowing progress] Support needed: [one specific ask from trainer or coordinator] Format: Subject: [Project Name] · Sprint [N] · Week [N] Update Opening: One sentence on overall team momentum Accomplishments: 3 bullet points Status: RAG indicator + one sentence explanation Blocker: One paragraph (max 3 sentences) Ask: One clear, specific request Under 200 words total. Professional but not stiff.

FAQ Page Content Generator S2–S3

Builder▼

Purpose

I need to write a FAQ page for [product/service] that addresses the real objections and questions a new user would have — not the questions we wish they were asking.

Example

Like Stripe's or Linear's FAQ pages — specific, honest, written from the user's perspective. Each question should be the actual thing someone would type in a search bar. Answers should be direct — no corporate hedging.

Expected Output

8 FAQ entries in Q&A format. Each question: max 12 words (written from user's perspective). Each answer: max 60 words (direct, no hedging). Group in 2 categories: Getting Started (4) and How It Works (4).

Write an FAQ page for [project/product name]: [one-sentence description]. Target user: [describe] Top 3 concerns users have about products like ours: [list 3 real objections or fears] Produce 8 FAQ entries grouped in 2 categories: GETTING STARTED (4 questions): Focus on: what it is, how to begin, who it's for, what it costs HOW IT WORKS (4 questions): Focus on: the process, what users need to do, what happens next, what guarantees exist Format: Q: [max 12 words — write from user's perspective, not yours] A: [max 60 words — direct, specific, no corporate hedging] Do not answer questions users are not actually asking. Address the real objections first.

🛠 Build Your Own PEX Prompt

Fill in the three PEX components below. The tool assembles a clean, copy-ready prompt.

P — Purpose (What do you need and why?)

E — Example (Tone, style, or comparable output)

X — Expected Output (Format, length, structure)

Maintaining your Prompt Library in the shared Drive:
Create a Google Sheet with columns: Prompt ID · Sprint · Role · Task Category · Purpose (brief) · Full Prompt · Output Quality (1–5) · Notes. Update after every significant AI interaction. The Scout is responsible for testing alternative prompts and recording comparisons. By Sprint 4, a strong team's library contains 25–40 entries — one of the most valuable artefacts from the programme.

Menu

PEX Prompt Library

The Notebook First Rule — Non-Negotiable

🛠 Build Your Own PEX Prompt